Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0955

reference
664-tree-1
name
0955
tree-preservation-order

undefined

664-tpo-1
uprn
address-text
point
POINT (-1.013387 50.867491)
geometry
MULTIPOLYGON (((-1.013345 50.867486,-1.013346 50.867495,-1.013352 50.867502,-1.013362 50.867508,-1.013373 50.867512,-1.013387 50.867514,-1.013400 50.867513,-1.013412 50.867509,-1.013421 50.867503,-1.013428 50.867495,-1.013430 50.867487,-1.013428 50.867479,-1.013422 50.867471,-1.013413 50.867465,-1.013401 50.867461,-1.013388 50.867460,-1.013375 50.867461,-1.013363 50.867465,-1.013353 50.867471,-1.013347 50.867478,-1.013345 50.867486)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL